XCO Limitations

XCO has the following limitations:

• Hostname or DNS name based device discovery is not supported.
• Device location cannot be modified after discovery.
• CLI support is not available for visibility skill.
• Only live statistics data streaming is supported.
• Secured Syslog configuration is not supported for MLX devices.
• User-defined access list (UDA) configuration is not migrated while configuration migration from an SLX or MLX to 9920.
• Listener policy byte count is incorrect for 9920 when truncation is enabled.
• Special characters such as %, {, }, \, and = are not supported in Name fields.
• If a device configured with both IPv4 and IPv6 addresses is discovered, only one entry is added to XCO. The first discovered IP address is used for communicating with that device.
• Device discovery failure is not listed on the Device log page for non-packet broker devices in the packet broker mode.
• All configurations are reverted when a port channel deployment fails. However, a LAG is created and deleted immediately, and the events are captured in the device logs.
• XCO 3.6.0 supports LAG hash masking options for port-channel load balancing on packet broker devices from Extreme 9920 Software release 21.2.2.0.
• Firmware upgrade requires an absolute path to the image location.